View Issue Details

IDProjectCategoryView StatusLast Update
0001173T99X171.00 SKB EagleSWpublic2021-06-23 14:25
Reporter(ALTech) Younkwang Jung Assigned To(SW) Kerwin Chen Due Date
PriorityurgentSeveritys2-severeReproducibilityhave not tried
Status closedResolutionreopened 
Summary0001173: [SMART3][BTF] BMT Issue occurred during BA01 RCU re-pairing after BA02 RCU pairing in RCU BA01 pairing state
DescriptionHi kerwin

We are currently testing BMT. a quick update is required for this issue.

The method of reproducing an issue is as follows.
1) pairing RCU(BA01) and STB1
2) pairing RCU(BA02) and STB1
3) pairing RCU(BA01) and STB1 ( An error occurs in this case. , Code11 )

Please check it why this issue is happening.(urgent)

Thanks
YK.Jung
TagsNo tags attached.
Attach Tags

Users monitoring this issue

User List (ALTech) SY Yoon , (SW) Jim Chen , (SW) Kerwin Chen , (SW) River Wong

Activities

(ALTech) Younkwang Jung

2021-03-19 10:37

developer   ~0006450

Hi Kerwin

This is an update from the RCU manager.

Similar issue is occurring in other way.
1. How to reproduce an issue
1-1. Clear Audio and BLE Bonding information from STB after BMM-BA01 and STB normal pairing
     (Google Settings-Remotes and Accessories)
1-2. The process in 1-1 automatically disconnects the BT connection between the RCU and the STB
     and the RCU enters the Direct Advertising state.
1-3. Re-Pairing on RCU ([*]+[#])

Re-Pairing in RCU may also be connected again
However, STB is occasionally unable to find BLE
In this case, the STB can find the BLE by rebooting STB

Please check the cause of this issue. I attach a logs ( logcat / BLE airlog )

1) BMM-BA01 and STB First Normal Pairing Log
    BFX-AT100_20210318-205306.zip
    210318_BMM_BA01_First_Pairing_BLE.zip
2) Issue Log when attempting to connect RCU Re-Pairing ([#]+[*]) after deleting RCU pairing information from STB
    210318_BMM_BA01_Repairing_On_DirectAdvertising[STB_Bonded_Info_Erased].zip
    BFX-AT100_20210318-205738.zip
3) Log where STB does not attempt to connect BLE to RCU during RCU Re-Pairing
    210318_BMM_BA02_STB_Not_Try_to_BLE_Connection.zip
    BFX-AT100_20210318-211203.zip

I will let you know if there is any additional update.
Thanks
YK.Jung

(ALTech) Younkwang Jung

2021-03-22 10:15

developer   ~0006472

Reminder sent to: (SW) Kerwin Chen

(ALTech) Younkwang Jung

2021-03-23 08:01

developer   ~0006481

Hi Kerwin

The level(seriousness) of this issue is increasing now.
The cause analysis is required why the RCU cannot be found on the STB.
Why RCU search is possible after reboot.

Please update it quickly.

Thanks
YK.Jung

(SW) Kerwin Chen

2021-03-23 14:07

developer   ~0006485

Hi YK. Jung,

It looks like an old issue. (https://mantis.cnsbg.foxconn.com/vaas/view.php?id=773)
Sometimes re-plug RCU battery will also make repairing successfully.
BTW, I think users don't do RCU repairing for many times.

Thanks !

(SW) Kerwin Chen

2021-03-23 20:11

developer   ~0006490

Hi YK Jung,

For "3) Log where STB does not attempt to connect BLE to RCU during RCU Re-Pairing", we think it is not a problem.
From "BFX-AT100_20210318-211203.zip" log files, RCU vendor tried to do RCU re-pairing in "Remote & Accessories" of TVSetting.
Therefore, SPTek's pairing APP can't receive scan results for pairing.

You can try to do re-pairing in the same page and check for the log.
It should be similar with log from RCU vendor.
Please check if RCU vendor where they did RCU re-pairing.
Thanks !

============================= logcat.log ========================================
...
03-18 21:09:38.922 3803 4048 I ActivityTaskManager: START u0 {cmp=com.android.tv.settings/.accessories.AddAccessoryActivity} from uid 1000 < ==== Enter "Remote & Accessories" of TVSetting
....
03-18 21:09:44.724 3803 3899 D WindowManager: interceptSkbFuctionKeyBeforeDispatching keycode = 394 < ==== RCU re-pairing key
....
03-18 21:09:44.727 6709 6709 D BtvBtPairingService: sptek:BT onStartCommand appVersion = 1.3.3, date = 2021.02.16 < ==== Start SPTek re-pairing service
03-18 21:09:45.071 6709 6709 E BtvBtPairingService: sptek:BT HID Key input onReceive->startScanning()
03-18 21:09:45.073 6709 6709 D BtvBtPairingService: sptek:BT startScanning controlState = 0
03-18 21:09:45.073 6709 6709 D BtvBtPairingService: sptek:BT startScanning cachedDevices size = 0
03-18 21:09:45.075 6709 6709 E BtvBtPairingService: sendBroadcastNaviLog function = pairing, state = start, reason = , name =
03-18 21:09:45.077 6709 6709 D BtvBtPairingService: sptek:BT sendDelayMessage message id = MSG_CONNECTING_TIMEOUT : Connecting 타임아웃time : 20000ms
03-18 21:09:45.077 6709 6709 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
....
03-18 21:09:46.005 3941 4086 D bt_btif_config: btif_get_device_type: Device [00:13:7b:3b:55:48] type 2 <=== RCU is found by STB
03-18 21:09:46.013 4073 4073 D BluetoothDevicePairer: Adding device: 00:13:7B:3B:55:48
03-18 21:09:46.016 4073 4073 D BluetoothDevicePairer: Added device to visible list. Name = BMM_BA01_548 , class = 1292
...
03-18 21:10:05.115 6709 6709 D BtvBtPairingService: sptek:BT Scanning timeout Stop
03-18 21:10:05.119 6709 6709 E BtvBtPairingService: sendBroadcastNaviLog function = pairing, state = fail, reason = scan[33], name = <=== pairing fail due to fail to receive scan result
03-18 21:10:05.123 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = false scanning = true
03-18 21:10:05.124 6709 6709 D BtvBtPairingService: sptek:BT checkStbItem() controlState = 0
03-18 21:10:05.124 6709 6709 D BtvBtPairingService: sptek:BT STB Item NULL
03-18 21:10:05.124 6709 6709 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
03-18 21:10:09.145 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = true scanning = false
....
03-18 21:10:19.132 3803 3899 D WindowManager: interceptSkbFuctionKeyBeforeDispatching keycode = 394
..
03-18 21:10:19.137 6709 6709 D BtvBtPairingService: sptek:BT onStartCommand appVersion = 1.3.3, date = 2021.02.16
03-18 21:10:19.443 6709 6709 E BtvBtPairingService: sptek:BT HID Key input onReceive->startScanning()
03-18 21:10:19.444 6709 6709 D BtvBtPairingService: sptek:BT startScanning controlState = 0
03-18 21:10:19.444 6709 6709 D BtvBtPairingService: sptek:BT startScanning cachedDevices size = 0
03-18 21:10:19.446 6709 6709 E BtvBtPairingService: sendBroadcastNaviLog function = pairing, state = start, reason = , name =
03-18 21:10:19.447 6709 6709 D BtvBtPairingService: sptek:BT sendDelayMessage message id = MSG_CONNECTING_TIMEOUT : Connecting 타임아웃time : 20000ms
03-18 21:10:19.448 6709 6709 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
...
03-18 21:10:20.355 3941 4086 D bt_btif_config: btif_get_device_type: Device [00:13:7b:3b:55:48] type 2
...
03-18 21:10:36.029 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = false scanning = true
03-18 21:10:36.029 6709 6709 D BtvBtPairingService: sptek:BT checkStbItem() controlState = 0
03-18 21:10:36.029 6709 6709 D BtvBtPairingService: sptek:BT STB Item NULL
03-18 21:10:36.029 6709 6709 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
03-18 21:10:40.047 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = true scanning = false
....
03-18 21:10:45.345 3803 3899 D WindowManager: interceptSkbFuctionKeyBeforeDispatching keycode = 394
....
03-18 21:10:45.348 6709 6709 D BtvBtPairingService: sptek:BT onStartCommand appVersion = 1.3.3, date = 2021.02.16
03-18 21:10:45.653 6709 6709 E BtvBtPairingService: sptek:BT HID Key input onReceive->startScanning()
03-18 21:10:45.654 6709 6709 D BtvBtPairingService: sptek:BT startScanning controlState = 0
03-18 21:10:45.654 6709 6709 D BtvBtPairingService: sptek:BT startScanning cachedDevices size = 0
03-18 21:10:45.656 6709 6709 E BtvBtPairingService: sendBroadcastNaviLog function = pairing, state = start, reason = , name =
03-18 21:10:45.657 6709 6709 D BtvBtPairingService: sptek:BT sendDelayMessage message id = MSG_CONNECTING_TIMEOUT : Connecting 타임아웃time : 20000ms
03-18 21:10:45.657 6709 6709 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
...
03-18 21:10:46.353 3941 4086 D bt_btif_config: btif_get_device_type: Device [00:13:7b:3b:55:48] type 2
03-18 21:10:46.712 3941 4086 D bt_btif_config: btif_get_device_type: Device [d0:03:df:a7:0c:49] type 3
...
03-18 21:10:59.246 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = false scanning = true
03-18 21:10:59.246 6709 6709 D BtvBtPairingService: sptek:BT checkStbItem() controlState = 0
03-18 21:10:59.246 6709 6709 D BtvBtPairingService: sptek:BT STB Item NULL
03-18 21:10:59.246 6709 6709 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
03-18 21:11:03.269 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = true scanning = false
....
03-18 21:11:23.048 3803 3899 D WindowManager: interceptSkbFuctionKeyBeforeDispatching keycode = 394
...
03-18 21:11:23.052 6709 6709 D BtvBtPairingService: sptek:BT onStartCommand appVersion = 1.3.3, date = 2021.02.16
03-18 21:11:23.363 6709 6709 E BtvBtPairingService: sptek:BT HID Key input onReceive->startScanning()
03-18 21:11:23.364 6709 6709 D BtvBtPairingService: sptek:BT startScanning controlState = 0
03-18 21:11:23.365 6709 6709 D BtvBtPairingService: sptek:BT startScanning cachedDevices size = 0
03-18 21:11:23.368 6709 6709 E BtvBtPairingService: sendBroadcastNaviLog function = pairing, state = start, reason = , name =
03-18 21:11:23.369 6709 6709 D BtvBtPairingService: sptek:BT sendDelayMessage message id = MSG_CONNECTING_TIMEOUT : Connecting 타임아웃time : 20000ms
03-18 21:11:23.369 6709 6709 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
03-18 21:11:27.159 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = false scanning = true
03-18 21:11:27.159 6709 6709 D BtvBtPairingService: sptek:BT checkStbItem() controlState = 0
03-18 21:11:27.159 6709 6709 D BtvBtPairingService: sptek:BT STB Item NULL
03-18 21:11:27.159 6709 6709 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
....
03-18 21:11:31.180 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = true scanning = false
....
03-18 21:11:31.853 3941 4086 D bt_btif_config: btif_get_device_type: Device [00:13:7b:3b:55:48] type 2
03-18 21:11:31.868 3941 4086 D bt_btif_config: btif_get_device_type: Device [70:82:6f:9d:d0:cc] type 2
03-18 21:11:31.893 3941 4086 D bt_btif_config: btif_get_device_type: Device [30:21:29:31:8c:63] type 1
....
03-18 21:11:49.255 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = false scanning = false
03-18 21:11:49.257 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = false scanning = false
....
03-18 21:11:49.249 3521 3874 E BufferQueueProducer: [com.android.tv.settings/com.android.tv.settings.accessories.AddAccessoryActivity#0] disconnect: not connected (req=1) < ==== Leave "Remote & Accessories"
....
03-18 21:11:50.298 3803 4967 I ActivityTaskManager: START u0 {cmp=com.android.tv.settings/.accessories.AddAccessoryActivity} from uid 1000 < ==== Enter "Remote & Accessories" of TVSetting
....
03-18 21:11:50.367 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = true scanning = false
03-18 21:12:10.722 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = false scanning = false
03-18 21:12:14.735 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = true scanning = false
...
03-18 21:12:23.805 3803 3899 D WindowManager: interceptSkbFuctionKeyBeforeDispatching keycode = 394
....
03-18 21:12:23.809 6709 6709 D BtvBtPairingService: sptek:BT onStartCommand appVersion = 1.3.3, date = 2021.02.16
03-18 21:12:24.114 6709 6709 E BtvBtPairingService: sptek:BT HID Key input onReceive->startScanning()
03-18 21:12:24.115 6709 6709 D BtvBtPairingService: sptek:BT startScanning controlState = 0
03-18 21:12:24.115 6709 6709 D BtvBtPairingService: sptek:BT startScanning cachedDevices size = 0
03-18 21:12:24.117 6709 6709 E BtvBtPairingService: sendBroadcastNaviLog function = pairing, state = start, reason = , name =
03-18 21:12:24.119 6709 6709 D BtvBtPairingService: sptek:BT sendDelayMessage message id = MSG_CONNECTING_TIMEOUT : Connecting 타임아웃time : 20000ms
03-18 21:12:24.119 6709 6709 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
03-18 21:12:35.212 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = false scanning = true
03-18 21:12:35.212 6709 6709 D BtvBtPairingService: sptek:BT checkStbItem() controlState = 0
03-18 21:12:35.212 6709 6709 D BtvBtPairingService: sptek:BT STB Item NULL
03-18 21:12:35.213 6709 6709 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
03-18 21:12:39.232 6709 6709 D BtvBtPairingService: sptek:BT onScanningStateChanged started = true scanning = false
....
03-18 21:12:39.345 3941 4086 D bt_btif_config: btif_get_device_type: Device [30:21:29:31:8c:63] type 1
03-18 21:12:39.580 3941 4086 D bt_btif_config: btif_get_device_type: Device [00:13:7b:3b:55:48] type 2
03-18 21:12:39.883 3941 4086 D bt_btif_config: btif_get_device_type: Device [d0:03:df:a7:0c:49] type 3
03-18 21:12:40.236 3941 4086 D bt_btif_config: btif_get_device_type: Device [d0:03:df:a7:0c:49] type 3
03-18 21:12:40.268 3941 4086 D bt_btif_config: btif_get_device_type: Device [7c:b4:4c:ff:a8:0a] type 2
...

(ALTech) Younkwang Jung

2021-03-23 20:53

developer   ~0006492

Hi kerwin

I wrote down the method of reproduction above
Have you tried reproducing this issue yourself?
I think if you test it yourself, you can figure out what's causing it. and we can talk to SKB with our test results.

Let's talk about this again tomorrow.

Thank you
YK.Jung
BRM_BA01_connection_fail.log (51,964 bytes)   
< BRM_BA01_connection_fail.log > 


BFX-AT100:/ # logcat
--------- beginning of main
03-23 20:26:57.767  6913  7021 I chromium: [6913:7021:INFO:mdns_app_filter.cc(2613)] MdnsAppFilter: responses sent in 102 seconds: 14
03-23 20:26:58.506  6913  6956 E chromium: [6913:6956:ERROR:ssl_tcp_socket_connector.cc(292)] SSL Connection timed out: 192.168.201.32:10101
03-23 20:26:58.507  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(261)] Failed to connect to parent
03-23 20:26:58.660  3522  3522 D isqmsAgent: [isqmsAgent 0883 03/23 20:26:58:660][3522] CISQMSSchedule::SCHETYPE_CYCLE event_id=H01
03-23 20:26:59.956  7981 10029 E memtrack: Couldn't load memtrack module
03-23 20:26:59.956  7981 10029 W android.os.Debug: failed to get memory consumption info: -1
03-23 20:27:00.334  7640  7640 D MDNSService: MDNSMsgHandler() AM_EVENT_CHECK_NETWORK_CONFIG. isConnected : true
03-23 20:27:02.069  3522  5941 D isqmsAgent: check_system_status
03-23 20:27:02.069  3522  5941 D isqmsAgent: CISQMSEnvm get_system_info
03-23 20:27:02.069  3522  5941 D isqmsAgent: CISQMSSystemInfo get_cpu_usage
03-23 20:27:02.069  3522  5941 D isqmsAgent: CISQMSSystemInfo get_cpu_usage 0x001
03-23 20:27:02.069  3522  5941 D isqmsAgent: read_process_status
03-23 20:27:02.069  3522  5941 D isqmsAgent: diff_process_status
03-23 20:27:02.069  3522  5941 D isqmsAgent: CISQMSSystemInfo get_cpu_usage 0x002
03-23 20:27:02.069  3522  5941 D isqmsAgent: CISQMSSystemInfo get_cpu_usage 0x003
03-23 20:27:02.069  3522  5941 D isqmsAgent: idle=17827  total=20383
03-23 20:27:02.069  3522  5941 D isqmsAgent: CISQMSSystemInfo get_cpu_usage 0x004
03-23 20:27:02.069  3522  5941 D isqmsAgent: cpu_usage=13 idle=17827  total=20383
03-23 20:27:02.069  3522  5941 D isqmsAgent: CISQMSSystemInfo get_system_memory
03-23 20:27:02.069  3522  5941 D isqmsAgent: CISQMSSystemInfo get_system_memory 0x001
03-23 20:27:02.069  3522  5941 D isqmsAgent: CISQMSSystemInfo get_system_memory 0x002
03-23 20:27:02.070  3522  5941 D isqmsAgent: CISQMSSystemInfo get_system_memory 0x003
03-23 20:27:02.070  3522  5941 D isqmsAgent: MEM total= 3063328 free= 408112 buffers =1368344 cached=40220 current=51
03-23 20:27:02.070  3522  5941 D isqmsAgent: CISQMSEnvm get_system_info
03-23 20:27:02.660  3522  3522 D isqmsAgent: [isqmsAgent 0884 03/23 20:27:02:660][3522] CISQMSSchedule::SCHETYPE_CYCLE event_id=H01
03-23 20:27:03.502  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 05A58FC1662A0BC09482BAA469222FDF; resolving...
03-23 20:27:03.748  3484  3484 E health2 : /sys/block/sda/stat: ReadFileToString failed.
03-23 20:27:04.375  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 2F6F45CA8DA23741B416C86FFB69BF9E; resolving...
03-23 20:27:05.334  7640  7640 D MDNSService: MDNSMsgHandler() AM_EVENT_CHECK_NETWORK_CONFIG. isConnected : true
03-23 20:27:05.584  6189  6280 D AGENT   : ^^device address : 40:19:20:20:7C:C5
03-23 20:27:05.584  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>20:73:3E |
03-23 20:27:05.584  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>8C:08:8B |
03-23 20:27:05.584  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>00:13:7B |
03-23 20:27:05.584  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>14:4E:34 |
03-23 20:27:05.584  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>9C:AC:6D |
03-23 20:27:05.584  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>40:19:20 |
03-23 20:27:05.584  6189  6280 D AGENT   : ###remoconisPairing : true
03-23 20:27:05.584  6189  6280 D AGENT   : ###remoconisConnected : false
03-23 20:27:05.588  6189  6280 D AGENT   : ^^device address : 40:19:20:20:7C:C5
03-23 20:27:05.588  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>20:73:3E |
03-23 20:27:05.588  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>8C:08:8B |
03-23 20:27:05.589  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>00:13:7B |
03-23 20:27:05.589  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>14:4E:34 |
03-23 20:27:05.589  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>9C:AC:6D |
03-23 20:27:05.589  6189  6280 D AGENT   : ^^^device address : 40:19:20:20:7C:C5 token=>>>40:19:20 |
03-23 20:27:05.589  6189  6280 I AGENT   : send_data=;100;1;0;40:19:20:20:7C:C5
03-23 20:27:05.589  6189  6280 D isqms_agent: ###### CISQMS::set_data nCategoryID=1, SubCategoryID=5, nFieldID=-1, dataLen = 26, pData=;100;1;0;40:19:20:20:7C:C5
03-23 20:27:05.589  6189  6280 D isqms_agent: INFO:push_data nType=2
03-23 20:27:05.589  6189  6280 D isqms_agent: @@@@@@@@@@@@@@@@@@@@@@@ push m_nEventCnt =  1
03-23 20:27:05.720  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 2F6F45CA8DA23741B416C86FFB69BF9E; resolving...
03-23 20:27:05.720  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 05A58FC1662A0BC09482BAA469222FDF; resolving...
03-23 20:27:06.546  6189  6273 D isqms_agent: success open fifo file=/btv_home/run/isqms_unix_socket_agent
03-23 20:27:06.546  6189  6273 D isqms_agent: CISQMS::make_msg2
03-23 20:27:06.546  6189  6273 D isqms_agent: CISQMS::make_msg SEND_DATA
03-23 20:27:06.546  6189  6273 D isqms_agent: send data=$send_data$1$5$-1$;100;1;0;40:19:20:20:7C:C5
03-23 20:27:06.546  6189  6273 D isqms_agent: send_data_to_agent sock write
03-23 20:27:06.547  3522  3552 D isqmsAgent: read data buffer=>$send_data$1$5$-1$;100;1;0;40:19:20:20:7C:C5
03-23 20:27:06.547  3522  3552 D isqmsAgent: read data pData=>$send_data$1$5$-1$;100;1;0;40:19:20:20:7C:C5
03-23 20:27:06.547  6189  6273 D isqms_agent: send_data_to_agent sock close
03-23 20:27:06.547  3522  3552 D isqmsAgent: INFO: ipc_data pData=$send_data$1$5$-1$;100;1;0;40:19:20:20:7C:C5
03-23 20:27:06.547  6189  6273 D isqms_agent: ######################## pop_data nType=2, m_nEventCnt=1, isqms->m_pISQMDATA=0
03-23 20:27:06.547  3522  3552 D isqmsAgent: nCategoryID=1, nSubCategoryID=5, nFieldID=-1
03-23 20:27:06.547  6189  6273 D isqms_agent: @@@@@@@@@@@@@@@@@@@@@@@ send delete m_nEventCnt =  1
03-23 20:27:06.547  3522  3552 D isqmsAgent: nCategoryID=1, nSubCategoryID=5, nFieldID=-1, pszPtr=;100;1;0;40:19:20:20:7C:C5, len = 26
03-23 20:27:06.547  6189  6273 D isqms_agent: @@@@@@@@@@@@@@@@@@@@@@@1 m_nEventCnt=0, isqms->m_pISQMDATA=0
03-23 20:27:06.547  3522  3552 D isqmsAgent: CISQMS:set_data nCategoryID=1, SubCategoryID=5, nFieldID=-1, pData=;100;1;0;40:19:20:20:7C:C5
03-23 20:27:06.547  3522  3552 D isqmsAgent: [isqmsAgent 0885 03/23 20:27:06:547][3522] INFO: get_property_value value=
03-23 20:27:06.547  3522  3552 D isqmsAgent: [isqmsAgent 0886 03/23 20:27:06:547][3522] INFO: get_property_value value=
03-23 20:27:06.547  3522  3552 D isqmsAgent: [isqmsAgent 0887 03/23 20:27:06:547][3522] INFO: get_property_value value=
03-23 20:27:06.547  3522  3552 D isqmsAgent: CISQMSData::set_sub_category_data battery=, manu=, ver=, pData=;100;1;0;40:19:20:20:7C:C5;;;
03-23 20:27:06.547  3522  3552 D isqmsAgent: _thread_read_data_from_agent_fifo running, recvthread
03-23 20:27:06.547  3522  3552 D isqmsAgent: _thread_read_data_from_agent_fifo read waiting
03-23 20:27:06.547  3522  3552 D isqmsAgent: read data buffer=>@@
03-23 20:27:06.547  3522  3552 D isqmsAgent: _thread_read_data_from_agent_fifo running, recvthread
03-23 20:27:06.548  3522  3552 D isqmsAgent: _thread_read_data_from_agent_fifo read waiting
03-23 20:27:06.549  6189  6273 D isqms_agent: @@@@@@@@@@@@@@@@@@@@@@@2 m_nEventCnt=0, isqms->m_pISQMDATA=0
03-23 20:27:06.661  3522  3522 D isqmsAgent: [isqmsAgent 0888 03/23 20:27:06:660][3522] CISQMSSchedule::SCHETYPE_CYCLE event_id=H01
03-23 20:27:07.100  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(289)] 11B352D5E98E4182B2A3299F857EFB00 Become root
03-23 20:27:08.545  6913  6956 E chromium: [6913:6956:ERROR:ssl_tcp_socket_connector.cc(292)] SSL Connection timed out: 192.168.201.32:10101
03-23 20:27:08.546  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(261)] Failed to connect to parent
03-23 20:27:10.335  7640  7640 D MDNSService: MDNSMsgHandler() AM_EVENT_CHECK_NETWORK_CONFIG. isConnected : true
03-23 20:27:10.543  6755  6804 I Finsky  : [284] nny.run(3): Stats for Executor: BlockingExecutor nqe@8cc3914[Running, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 153]
03-23 20:27:10.544  6755  6804 I Finsky  : [284] nny.run(3): Stats for Executor: LightweightExecutor nqe@1d095bd[Running, pool size = 3, active threads = 0, queued tasks = 0, completed tasks = 300]
03-23 20:27:10.661  3522  3522 D isqmsAgent: [isqmsAgent 0889 03/23 20:27:10:661][3522] CISQMSSchedule::SCHETYPE_CYCLE event_id=H01
03-23 20:27:13.542  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 05A58FC1662A0BC09482BAA469222FDF; resolving...
03-23 20:27:13.775  6755  6804 I Finsky  : [284] nny.run(3): Stats for Executor: bgExecutor nqe@e0dbee2[Running, pool size = 4, active threads = 0, queued tasks = 0, completed tasks = 708]
03-23 20:27:14.013  3812  3977 D WindowManager: interceptKeyTq keycode=394 interactive=true keyguardActive=false policyFlags=22000000
03-23 20:27:14.016  3812  3976 D WindowManager: interceptKeyTi keyCode=394 down=true repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=2 mSource=1793 mScanCode=481 mCharacters=null
03-23 20:27:14.016  3812  3976 D WindowManager: interceptKeyTi strDate 2021-03-23 20:27
03-23 20:27:14.017  3812  3976 D WindowManager: interceptSkbFuctionKeyBeforeDispatching keycode = 394
03-23 20:27:14.017  3812  3976 D WindowManager: keycode : 394 - processed. by skb function key
03-23 20:27:14.095  3812  3977 D WindowManager: interceptKeyTq keycode=394 interactive=true keyguardActive=false policyFlags=22000000
03-23 20:27:14.095  3812  3976 D WindowManager: interceptKeyTi keyCode=394 down=false repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=2 mSource=1793 mScanCode=481 mCharacters=null
03-23 20:27:14.095  3812  3976 D WindowManager: interceptSkbFuctionKeyBeforeDispatching keycode = 394
--------- beginning of system
03-23 20:27:14.096  3812  3976 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.startService:1570 com.android.server.policy.PhoneWindowManager.interceptSkbFuctionKeyBeforeDispatching:2935 com.android.server.policy.PhoneWindowManager.interceptKeyBeforeDispatchingInner:3164 com.android.server.policy.PhoneWindowManager.interceptKeyBeforeDispatching:3084 com.android.server.wm.InputManagerCallback.interceptKeyBeforeDispatching:183
03-23 20:27:14.096  5712  5712 D BtvService0.1.36 IBtvService: BTF|onReceive|72|IN|  DeviceCtrlServiceReceiver::onReceive action = com.skb.intent.KEY_LED_BLINK, BUILD_DATE:2021.02.08
03-23 20:27:14.097  3812  3976 D WindowManager: keycode : 394 - processed. by skb function key
03-23 20:27:14.097  7455  7455 D BtvBtPairingService: sptek:BT onStartCommand appVersion = 1.3.2, date = 2020.10.21
03-23 20:27:14.097  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp
03-23 20:27:14.098  5712  5712 D BtvService0.1.36 IBtvService: BTF|onReceive|482| DeviceCtrlServiceReceiver::onReceive : call getFrontPanel().setLedState, lastKeyTime= 2021-03-23 20:27
03-23 20:27:14.098  5712  5712 D BtvJniInterface: BTF|setLastKeyTime|996|setLastKeyTime keyTime: 2021-03-23 20:27
03-23 20:27:14.098  5712  5712 D BTVCORE-JNI: tvcoreJni_setLastKeyTime start
03-23 20:27:14.098  5712  5712 D BTVCORE-JNI: [tvcoreJni_setLastKeyTime] keyTime(2021-03-23 20:27)
03-23 20:27:14.098  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BT02
03-23 20:27:14.098  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BRM_Audio02
03-23 20:27:14.098  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.098  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BT06
03-23 20:27:14.098  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BRM_Audio06
03-23 20:27:14.098  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.098  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BT07
03-23 20:27:14.098  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BRM_Audio07
03-23 20:27:14.099  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BT08
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BRM_Audio08
03-23 20:27:14.099  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BT09
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BRM_Audio09
03-23 20:27:14.099  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BT09
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BRM_Audio09
03-23 20:27:14.099  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BT10
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BRM_Audio10
03-23 20:27:14.099  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BT10
03-23 20:27:14.099  3845  3880 I TVService-21.02.06: [vendor/skb/framework/btf_dev/interface/btvservice/1.0/default/TVService.cpp][setLastKeyTime] called keyTime=(2021-03-23 20:27)
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BRM_Audio10
03-23 20:27:14.099  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BT11
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp =
03-23 20:27:14.099  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = false
03-23 20:27:14.099  3845  3880 I TVService-21.02.06: [TVService::setLastKeyTime] cKeyTime(2021-03-23 20:27)
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BA01
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BRM_Audio_BA01
03-23 20:27:14.099  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BA01
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BRM_Audio_BA01
03-23 20:27:14.099  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BRM_BA02
03-23 20:27:14.099  6203  6297 D UEI.SmartControl: File event:8
03-23 20:27:14.099  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp =
03-23 20:27:14.100  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = false
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BMM_BT02
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BMM_Audio02
03-23 20:27:14.100  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.100  5712  5712 D BTVCORE-JNI: tvcoreJni_frontPanelSetLedState start
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BMM_BT06
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BMM_Audio06
03-23 20:27:14.100  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BMM_BT07
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BMM_Audio07
03-23 20:27:14.100  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BMM_BT08
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BMM_Audio08
03-23 20:27:14.100  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BMM_BT09
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BMM_Audio09
03-23 20:27:14.100  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BMM_BT10
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BMM_Audio10
03-23 20:27:14.100  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BMM_BT11
03-23 20:27:14.100  3845  3880 I TVService-21.02.06: [TVService::frontPanelSetLedState] index(3) state(2).
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp =
03-23 20:27:14.100  3845  3880 I FrontPanelManager: [frontPanelSetLedState] called index(3) state(2)
03-23 20:27:14.100  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = false
03-23 20:27:14.100  3845  3880 D DEVICE  : BTF|DEVICE_SetLedState|85|IN| device:f3505050, led_id:3, state:2
03-23 20:27:14.100  3845  3880 D DEVICE  : ++DEVICE_SetLedState led_id(3), state(2)
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BMM_BA01
03-23 20:27:14.100  3845  3880 D hal_frontpanel: hal_frontpanel:HAL_FrontPanelSetLedState v102(3, 2)
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BMM_Audio_BA01
03-23 20:27:14.100  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BMM_BA02
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp =
03-23 20:27:14.100  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = false
03-23 20:27:14.100  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BUE_BT07
03-23 20:27:14.101  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BUE_Audio07
03-23 20:27:14.101  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.101  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BUE_BT09
03-23 20:27:14.101  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BUE_Audio09
03-23 20:27:14.101  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.101  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BUE_BT09
03-23 20:27:14.101  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BUE_Audio09
03-23 20:27:14.101  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.101  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BUE_SR01
03-23 20:27:14.101  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BUE_Audio_SR01
03-23 20:27:14.101  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.101  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BUE_SR01
03-23 20:27:14.101  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BUE_Audio_SR01
03-23 20:27:14.101  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.101  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp hid = BUE_SR01
03-23 20:27:14.101  7455  7455 E BtvBluetoothUtils: parsingXmlRcuProp a2dp = BUE_Audio_SR01
03-23 20:27:14.101  7455  7455 D BtvBluetoothUtils: parsingXmlRcuProp rcuSupport.isSupportA2dp  = true
03-23 20:27:14.202  3845  3880 D DEVICE  : BTF|DEVICE_SetLedState|111|OUT|
03-23 20:27:14.202  5712  5712 D BtvService0.1.36 IBtvService: BTF|onReceive|498|OUT|  DeviceCtrlServiceReceiver:: END
03-23 20:27:14.402  7455  7455 E BtvBtPairingService: sptek:BT HID Key input onReceive->startScanning()
03-23 20:27:14.403  7455  7455 E BtvBluetoothUtils: initCurrentRCU mCurrentRCU is NULL
03-23 20:27:14.403  7455  7455 D BtvBtPairingService: sptek:BT startScanning controlState = 0
03-23 20:27:14.403  7455  7455 D BtvBtPairingService: sptek:BT startScanning cachedDevices size = 1
03-23 20:27:14.408  7455  7455 D BtvBtPairingService: sptek:BT startScanning cachedDevices d.getName = BMM_BA02_CC5 bondState = BOND_BONDED_12, connect = true, isBusy = false
03-23 20:27:14.410  7455  7455 D BtvBluetoothUtils: isBTControl name = BMM_BA02_CC5
03-23 20:27:14.411  7455  7455 D BtvBluetoothUtils: isBTAudio name = BMM_BA02_CC5
03-23 20:27:14.412  7455  7455 E BtvBluetoothUtils: isBTAudio false
03-23 20:27:14.414  4498  8340 D BluetoothAdapterService: startDiscovery
03-23 20:27:14.416  4498  5016 E bt_btif : bte_scan_filt_param_cfg_evt, 1
03-23 20:27:14.416  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 2F6F45CA8DA23741B416C86FFB69BF9E; resolving...
03-23 20:27:14.416  4498  5016 E bt_btif : bte_scan_filt_param_cfg_evt, 1
03-23 20:27:14.416  4498  5016 W bt_btif : bta_dm_check_av:0
03-23 20:27:14.416  7455  7455 E BtvBtPairingService: sendBroadcastNaviLog function = pairing, state = start, reason = , name =
03-23 20:27:14.417  7455  7455 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1045 android.content.ContextWrapper.sendBroadcast:448 com.skb.btv.bluetooth.BtvBluetoothPairingService.sendBroadcastNaviLog:1183 com.skb.btv.bluetooth.BtvBluetoothPairingService.startScanning:397 com.skb.btv.bluetooth.BtvBluetoothPairingService.receiveBT:278
03-23 20:27:14.421  3812  5245 E ActivityManager: Sending non-protected broadcast com.skb.btv.intent.navilog.btrcu from system 7455:com.skb.btv.bluetooth/1000 pkg com.skb.btv.bluetooth
03-23 20:27:14.421  3812  5245 E ActivityManager: java.lang.Throwable
03-23 20:27:14.421  3812  5245 E ActivityManager:       at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:14809)
03-23 20:27:14.421  3812  5245 E ActivityManager:       at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:15450)
03-23 20:27:14.421  3812  5245 E ActivityManager:       at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:14826)
03-23 20:27:14.421  3812  5245 E ActivityManager:       at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:15592)
03-23 20:27:14.421  3812  5245 E ActivityManager:       at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:1950)
03-23 20:27:14.421  3812  5245 E ActivityManager:       at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2741)
03-23 20:27:14.421  3812  5245 E ActivityManager:       at android.os.Binder.execTransactInternal(Binder.java:1021)
03-23 20:27:14.421  3812  5245 E ActivityManager:       at android.os.Binder.execTransact(Binder.java:994)
03-23 20:27:14.423  3812  5245 I DropBoxManagerService: add tag=system_server_wtf isTagEnabled=true flags=0x2
03-23 20:27:14.428  7455  7455 D BtvBtPairingService: sptek:BT sendDelayMessage message id = MSG_CONNECTING_TIMEOUT : Connecting Ÿ�Ӿƿ�time : 20000ms
03-23 20:27:14.428  7455  7455 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
03-23 20:27:14.438  3812  7474 I ActivityManager: Killing 5520:com.google.process.gapps/u0a40 (adj 955): empty for 1806s
03-23 20:27:14.439  3812  7474 I ActivityManager: Killing 8164:com.google.android.gms.ui/u0a40 (adj 965): empty for 1809s
03-23 20:27:14.441  3812  7474 I ActivityManager: Killing 5208:android.process.acore/u0a10 (adj 965): empty for 1814s
03-23 20:27:14.442  3812  7474 I ActivityManager: Killing 5472:android.process.media/u0a5 (adj 975): empty for 1815s
03-23 20:27:14.455  3812  3959 I NotificationService: cancelToast pkg=com.skb.btv.bluetooth callback=android.app.ITransientNotification$Stub$Proxy@27c5bda
03-23 20:27:14.455  3812  3959 W NotificationService: Toast already cancelled. pkg=com.skb.btv.bluetooth callback=android.app.ITransientNotification$Stub$Proxy@27c5bda
03-23 20:27:14.455  7455  7455 D BtvBtPairingService: sptek:BT onScanningStateChanged started = true scanning = true
03-23 20:27:14.458  4498  4600 D bt_btif_config: btif_get_device_type: Device [40:19:20:60:01:2e] type 1
03-23 20:27:14.477  3542  3656 I [Gralloc]: ddebug, pair (share_fd=67, user_hnd=4, ion_client=26)
03-23 20:27:14.478  7455  8294 I [Gralloc]: ddebug, pair (share_fd=57, user_hnd=1, ion_client=60)
03-23 20:27:14.480  3542  3656 I [Gralloc]: ddebug, pair (share_fd=80, user_hnd=5, ion_client=26)
03-23 20:27:14.484  3542  3656 I [Gralloc]: ddebug, pair (share_fd=93, user_hnd=9, ion_client=26)
03-23 20:27:14.489  3461  3461 I Zygote  : Process 8164 exited due to signal 9 (Killed)
03-23 20:27:14.494  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = 40:19:20:60:01:2E, mIsAutoPairing = true, mControlState = 0
03-23 20:27:14.496  7455  7455 D BtvBluetoothUtils: isBTControl name = 40:19:20:60:01:2E
03-23 20:27:14.496  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: 40:19:20:60:01:2E
03-23 20:27:14.503  3461  3461 I Zygote  : Process 5208 exited due to signal 9 (Killed)
03-23 20:27:14.505  3812  3831 D CountryDetector: No listener is left
03-23 20:27:14.505  3461  3461 I Zygote  : Process 5520 exited due to signal 9 (Killed)
03-23 20:27:14.523  3461  3461 I Zygote  : Process 5472 exited due to signal 9 (Killed)
03-23 20:27:14.526  4498  4600 D bt_btif_config: btif_get_device_type: Device [40:19:20:60:00:15] type 1
03-23 20:27:14.527  3812  3863 I libprocessgroup: Successfully killed process cgroup uid 10040 pid 5520 in 87ms
03-23 20:27:14.528  3812  3863 I libprocessgroup: Successfully killed process cgroup uid 10040 pid 8164 in 0ms
03-23 20:27:14.529  3812  3863 I libprocessgroup: Successfully killed process cgroup uid 10010 pid 5208 in 0ms
03-23 20:27:14.530  3812  3863 I libprocessgroup: Successfully killed process cgroup uid 10005 pid 5472 in 0ms
03-23 20:27:14.531  3482  3616 I [Gralloc]: ddebug, pair (share_fd=44, user_hnd=1, ion_client=31)
03-23 20:27:14.535  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = BID-AT200, mIsAutoPairing = true, mControlState = 0
03-23 20:27:14.536  7455  7455 D BtvBluetoothUtils: isBTControl name = BID-AT200
03-23 20:27:14.536  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: 40:19:20:60:00:15
03-23 20:27:14.661  3522  3522 D isqmsAgent: [isqmsAgent 0890 03/23 20:27:14:661][3522] CISQMSSchedule::SCHETYPE_CYCLE event_id=H01
03-23 20:27:14.663  4498  4600 D bt_btif_config: btif_get_device_type: Device [ec:5c:68:1d:bd:f4] type 1
03-23 20:27:14.673  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = BFX-AT100, mIsAutoPairing = true, mControlState = 0
03-23 20:27:14.675  7455  7455 D BtvBluetoothUtils: isBTControl name = BFX-AT100
03-23 20:27:14.675  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: EC:5C:68:1D:BD:F4
03-23 20:27:14.677  4498  4600 D bt_btif_config: btif_get_device_type: Device [ec:5c:68:1d:bd:bb] type 1
03-23 20:27:14.688  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = BFX-AT100, mIsAutoPairing = true, mControlState = 0
03-23 20:27:14.690  7455  7455 D BtvBluetoothUtils: isBTControl name = BFX-AT100
03-23 20:27:14.690  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: EC:5C:68:1D:BD:BB
03-23 20:27:14.750  4498  5016 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet
03-23 20:27:14.753  4498  5016 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet
03-23 20:27:14.759  4498  4600 D bt_btif_config: btif_get_device_type: Device [f4:fe:fb:84:06:f9] type 3
03-23 20:27:14.765  4498  4600 D bt_btif_config: btif_get_device_type: Device [50:de:06:88:87:18] type 3
03-23 20:27:14.770  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = [TV] Samsung 7 Series (43), mIsAutoPairing = true, mControlState = 0
03-23 20:27:14.773  7455  7455 D BtvBluetoothUtils: isBTControl name = [TV] Samsung 7 Series (43)
03-23 20:27:14.773  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: F4:FE:FB:84:06:F9
03-23 20:27:14.774  4498  4600 D bt_btif_config: btif_get_device_type: Device [40:19:20:60:01:0d] type 3
03-23 20:27:14.779  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = 50:DE:06:88:87:18, mIsAutoPairing = true, mControlState = 0
03-23 20:27:14.783  7455  7455 D BtvBluetoothUtils: isBTControl name = 50:DE:06:88:87:18
03-23 20:27:14.783  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: 50:DE:06:88:87:18
03-23 20:27:14.792  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = BID-AT200, mIsAutoPairing = true, mControlState = 0
03-23 20:27:14.794  7455  7455 D BtvBluetoothUtils: isBTControl name = BID-AT200
03-23 20:27:14.794  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: 40:19:20:60:01:0D
03-23 20:27:14.868  4498  4600 D bt_btif_config: btif_get_device_type: Device [ec:5c:68:1d:be:6c] type 1
03-23 20:27:14.875  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = BFX-AT100, mIsAutoPairing = true, mControlState = 0
03-23 20:27:14.877  7455  7455 D BtvBluetoothUtils: isBTControl name = BFX-AT100
03-23 20:27:14.877  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: EC:5C:68:1D:BE:6C
03-23 20:27:14.907  4498  4600 D bt_btif_config: btif_get_device_type: Device [40:19:20:60:01:31] type 3
03-23 20:27:14.915  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = 40:19:20:60:01:31, mIsAutoPairing = true, mControlState = 0
03-23 20:27:14.919  7455  7455 D BtvBluetoothUtils: isBTControl name = 40:19:20:60:01:31
03-23 20:27:14.919  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: 40:19:20:60:01:31
03-23 20:27:15.117  4498  5016 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet
03-23 20:27:15.121  4498  5016 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet
03-23 20:27:15.334  7640  7640 D MDNSService: MDNSMsgHandler() AM_EVENT_CHECK_NETWORK_CONFIG. isConnected : true
03-23 20:27:15.352  4498  4600 D bt_btif_config: btif_get_device_type: Device [40:19:20:60:00:b9] type 1
03-23 20:27:15.360  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = 40:19:20:60:00:B9, mIsAutoPairing = true, mControlState = 0
03-23 20:27:15.362  7455  7455 D BtvBluetoothUtils: isBTControl name = 40:19:20:60:00:B9
03-23 20:27:15.363  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: 40:19:20:60:00:B9
03-23 20:27:15.462  4498  5016 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet
03-23 20:27:15.474  4498  5016 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet
03-23 20:27:15.555  4498  4600 D bt_btif_config: btif_get_device_type: Device [ec:5c:68:1d:be:81] type 1
03-23 20:27:15.570  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = BFX-AT100, mIsAutoPairing = true, mControlState = 0
03-23 20:27:15.574  7455  7455 D BtvBluetoothUtils: isBTControl name = BFX-AT100
03-23 20:27:15.575  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: EC:5C:68:1D:BE:81
03-23 20:27:15.756  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 2F6F45CA8DA23741B416C86FFB69BF9E; resolving...
03-23 20:27:15.757  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 05A58FC1662A0BC09482BAA469222FDF; resolving...
03-23 20:27:15.817  4498  4600 D bt_btif_config: btif_get_device_type: Device [14:4e:34:96:09:30] type 2
03-23 20:27:15.820  4498  5016 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet
03-23 20:27:15.821  4498  5016 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet
03-23 20:27:15.827  4498  4600 D bt_btif_config: btif_get_device_type: Device [40:19:20:60:01:12] type 3
03-23 20:27:15.829  4498  5016 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet
03-23 20:27:15.836  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = BRM_BA01_930, mIsAutoPairing = true, mControlState = 0
03-23 20:27:15.839  7455  7455 D BtvBluetoothUtils: isBTControl name = BRM_BA01_930
03-23 20:27:15.839  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded bt search success stopScanning
03-23 20:27:15.842  4498  8340 D BluetoothAdapterService: cancelDiscovery
03-23 20:27:15.843  4498  5016 E bt_btif : bte_scan_filt_param_cfg_evt, 1
03-23 20:27:15.843  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: 14:4E:34:96:09:30
03-23 20:27:15.851  7455  7455 D BtvBtPairingService: sptek:BT onDeviceAdded deviceName = 40:19:20:60:01:12, mIsAutoPairing = true, mControlState = 0
03-23 20:27:15.858  7455  7455 D BtvBluetoothUtils: isBTControl name = 40:19:20:60:01:12
03-23 20:27:15.858  7455  7455 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: 40:19:20:60:01:12
03-23 20:27:15.858  7455  7455 D BtvBtPairingService: sptek:BT onScanningStateChanged started = false scanning = true
03-23 20:27:15.859  7455  7455 D BtvBtPairingService: sptek:BT checkStbItem() controlState = 0
03-23 20:27:15.861  7455  7455 D BtvBtPairingService: sptek:BT checkStbItem mNewBTName = BRM_BA01_930 BTAddress = 14:4E:34:96:09:30
03-23 20:27:15.863  7455  7455 D BtvBtPairingService: sptek:BT STB Item Ok name = BRM_BA01_930
03-23 20:27:15.863  7455  7455 D BtvBtPairingService: sptek:BT pair()
03-23 20:27:15.865  7455  7455 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
03-23 20:27:15.874  7455  7455 I BluetoothDevice: createBond() for device 14:4E:34:96:09:30 called by pid: 7455 tid: 7455
03-23 20:27:15.875  4498  5016 E bt_btif : bte_scan_filt_param_cfg_evt, 1
03-23 20:27:15.876  7455  7455 D BtvBtPairingService: sptek:BT BRM_BA01_930 pair Success
03-23 20:27:15.876  7455  7455 D BtvBtPairingService: sptek:BT sendDelayMessage message id = MSG_CONNECTING_TIMEOUT : Connecting Ÿ�Ӿƿ�time : 10000ms
03-23 20:27:15.877  3542  3649 I [Gralloc]: ddebug, free share_fd=93, user_hnd=0x9, ion client=26
03-23 20:27:15.877  3542  3649 I [Gralloc]: ddebug, free share_fd=80, user_hnd=0x5, ion client=26
03-23 20:27:15.879  7455  8294 I [Gralloc]: ddebug, free share_fd=57, user_hnd=0x1, ion client=60
03-23 20:27:15.879  3542  3649 E BufferQueueProducer: [Toast#0] disconnect: not connected (req=1)
03-23 20:27:15.879  7455  8294 W libEGL  : EGLNativeWindowType 0xd6b170a8 disconnect failed
03-23 20:27:15.890  3812  6108 W WindowManager: removeWindowToken: Attempted to remove non-existing token: android.os.Binder@10956fc
03-23 20:27:15.890  3812  6108 I NotificationService: cancelToast pkg=com.skb.btv.bluetooth callback=android.app.ITransientNotification$Stub$Proxy@f9ab00
03-23 20:27:15.891  3812  6108 W WindowManager: removeWindowToken: Attempted to remove non-existing token: android.os.Binder@10956fc
03-23 20:27:15.894  7455  7455 D BtvBtPairingService: sptek:BT onScanningStateChanged started = false scanning = false
03-23 20:27:15.909  3542  3649 I [Gralloc]: ddebug, pair (share_fd=85, user_hnd=5, ion_client=26)
03-23 20:27:15.910  7455  8294 I [Gralloc]: ddebug, pair (share_fd=57, user_hnd=1, ion_client=60)
03-23 20:27:15.911  3542  3649 I [Gralloc]: ddebug, pair (share_fd=97, user_hnd=9, ion_client=26)
03-23 20:27:15.913  3542  3649 I [Gralloc]: ddebug, pair (share_fd=20, user_hnd=b, ion_client=26)
03-23 20:27:15.967  3482  3616 I [Gralloc]: ddebug, pair (share_fd=64, user_hnd=6, ion_client=31)
03-23 20:27:16.417  3482  3616 I [Gralloc]: ddebug, free share_fd=44, user_hnd=0x1, ion client=31
03-23 20:27:16.417  3482  3616 W gralloc : Warning shared attribute region mapped at free. Unmapping
03-23 20:27:16.430  3812  3860 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
03-23 20:27:16.431  3812  3860 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
03-23 20:27:16.433  3542  3542 I [Gralloc]: ddebug, free share_fd=67, user_hnd=0x4, ion client=26
03-23 20:27:17.138  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(289)] 11B352D5E98E4182B2A3299F857EFB00 Become root
03-23 20:27:17.460  5957  5957 D PASMainServiceReceiver: onReceive() - action : com.skb.stbPush.pasrestart
03-23 20:27:17.460  5957  5957 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.startService:1570 android.content.ContextWrapper.startService:669 android.content.ContextWrapper.startService:669 com.skb.stbPush.PASMainServiceReceiver.onReceive:27 android.app.ActivityThread.handleReceiver:3788
03-23 20:27:17.463  5957  5957 D PASMainService: [PAS]::onStartCommand()
03-23 20:27:17.557  4902  5019 I NetworkScheduler.Stats: Task com.google.android.gms/com.google.android.gms.checkin.EventLogService started execution. cause:4 exec_start_elapsed_seconds: 1950 [CONTEXT service_id=218 ]
03-23 20:27:17.580  5111  8248 I Checkin : [EventLogChimeraService] Opted in for usage reporting: false
03-23 20:27:17.580  5111  8248 I Checkin : [EventLogChimeraService] Aggregate from 1616497037117 (log), 1616497037117 (data)
03-23 20:27:17.620  3812  3831 I DropBoxManagerService: add tag=event_data isTagEnabled=true flags=0x2
03-23 20:27:17.684  3812  3860 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
03-23 20:27:17.685  3812  3860 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
03-23 20:27:17.725  4902  4961 I NetworkScheduler.Stats: Task com.google.android.gms/com.google.android.gms.checkin.EventLogService finished executing. cause:4 result: 1 elapsed_millis: 203 uptime_millis: 203 exec_start_elapsed_seconds: 1950 [CONTEXT service_id=218 ]
03-23 20:27:17.963  3812  3850 W WindowManager: Unable to start animation, surface is null or no children.
03-23 20:27:18.579  6913  6956 E chromium: [6913:6956:ERROR:ssl_tcp_socket_connector.cc(292)] SSL Connection timed out: 192.168.201.32:10101
03-23 20:27:18.580  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(261)] Failed to connect to parent
03-23 20:27:18.662  3522  3522 D isqmsAgent: [isqmsAgent 0891 03/23 20:27:18:662][3522] CISQMSSchedule::SCHETYPE_CYCLE event_id=H01
03-23 20:27:19.397  3542  6236 I [Gralloc]: ddebug, free share_fd=20, user_hnd=0xb, ion client=26
03-23 20:27:19.397  3542  6236 I [Gralloc]: ddebug, free share_fd=97, user_hnd=0x9, ion client=26
03-23 20:27:19.400  7455  8294 I [Gralloc]: ddebug, free share_fd=57, user_hnd=0x1, ion client=60
03-23 20:27:19.401  3542  6236 E BufferQueueProducer: [Toast#1] disconnect: not connected (req=1)
03-23 20:27:19.401  7455  8294 W libEGL  : EGLNativeWindowType 0xd6b170a8 disconnect failed
03-23 20:27:19.418  3812  7933 W NotificationService: Toast already killed. pkg=com.skb.btv.bluetooth callback=android.app.ITransientNotification$Stub$Proxy@b28d1db
03-23 20:27:19.920  3482  3616 I [Gralloc]: ddebug, free share_fd=64, user_hnd=0x6, ion client=31
03-23 20:27:19.920  3482  3616 W gralloc : Warning shared attribute region mapped at free. Unmapping
03-23 20:27:19.936  3542  3542 I [Gralloc]: ddebug, free share_fd=85, user_hnd=0x5, ion client=26
03-23 20:27:20.335  7640  7640 D MDNSService: MDNSMsgHandler() AM_EVENT_CHECK_NETWORK_CONFIG. isConnected : true
03-23 20:27:20.509  6913  6913 I chromium: [6913:6913:INFO:metrics_recorder.cc(110)] Metrics stat: total=4
03-23 20:27:20.509  6913  6913 I chromium: Cast.Discovery.Mdns.Request.In=8
03-23 20:27:20.509  6913  6913 I chromium: Cast.Discovery.Mdns.Response.Out=8
03-23 20:27:20.509  6913  6913 I chromium: CastV2.Transport.Ping.In=12
03-23 20:27:20.509  6913  6913 I chromium: CastV2.Transport.Pong.Out=12
03-23 20:27:22.262  6913  7021 I chromium: [6913:7021:INFO:mdns_app_filter.cc(2797)] Mdns cast queries recently sent: queries=2
03-23 20:27:22.662  3522  3522 D isqmsAgent: [isqmsAgent 0892 03/23 20:27:22:662][3522] CISQMSSchedule::SCHETYPE_CYCLE event_id=H01
03-23 20:27:23.583  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 05A58FC1662A0BC09482BAA469222FDF; resolving...
03-23 20:27:24.453  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 2F6F45CA8DA23741B416C86FFB69BF9E; resolving...
03-23 20:27:24.454  5135  5135 I QSM     : QSM check system info : mem_usage=50, cpu_usage=10, disk_usage=33
03-23 20:27:25.336  7640  7640 D MDNSService: MDNSMsgHandler() AM_EVENT_CHECK_NETWORK_CONFIG. isConnected : true
03-23 20:27:25.506  7075  7111 I Finsky:download_service: [302] nny.run(3): Stats for Executor: bgExecutor nqe@f539404[Running, pool size = 4, active threads = 0, queued tasks = 0, completed tasks = 44]
03-23 20:27:25.797  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 2F6F45CA8DA23741B416C86FFB69BF9E; resolving...
03-23 20:27:25.798  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 05A58FC1662A0BC09482BAA469222FDF; resolving...
03-23 20:27:25.911  7455  7455 D BtvBtPairingService: sptek:BT bonding timeout Stop
03-23 20:27:25.925  7455  7455 D BtvBtPairingService: sptek:BT initToast() mToast.cancel
03-23 20:27:25.950  3812  7933 I ActivityManager: Killing 7075:com.android.vending:download_service/u0a50 (adj 945): empty for 1800s
03-23 20:27:25.954  7455  7455 E BtvBtPairingService: sendBroadcastNaviLog function = pairing, state = fail, reason = pair[11], name =
03-23 20:27:25.955  7455  7455 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1045 android.content.ContextWrapper.sendBroadcast:448 com.skb.btv.bluetooth.BtvBluetoothPairingService.sendBroadcastNaviLog:1183 com.skb.btv.bluetooth.BtvBluetoothPairingService.access$700:60 com.skb.btv.bluetooth.BtvBluetoothPairingService$3.handleMessage:432
03-23 20:27:25.956  3812  7933 E ActivityManager: Sending non-protected broadcast com.skb.btv.intent.navilog.btrcu from system 7455:com.skb.btv.bluetooth/1000 pkg com.skb.btv.bluetooth
03-23 20:27:25.956  3812  7933 E ActivityManager: java.lang.Throwable
03-23 20:27:25.956  3812  7933 E ActivityManager:       at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:14809)
03-23 20:27:25.956  3812  7933 E ActivityManager:       at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:15450)
03-23 20:27:25.956  3812  7933 E ActivityManager:       at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:14826)
03-23 20:27:25.956  3812  7933 E ActivityManager:       at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:15592)
03-23 20:27:25.956  3812  7933 E ActivityManager:       at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:1950)
03-23 20:27:25.956  3812  7933 E ActivityManager:       at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2741)
03-23 20:27:25.956  3812  7933 E ActivityManager:       at android.os.Binder.execTransactInternal(Binder.java:1021)
03-23 20:27:25.956  3812  7933 E ActivityManager:       at android.os.Binder.execTransact(Binder.java:994)
03-23 20:27:25.958  3812  7933 I DropBoxManagerService: add tag=system_server_wtf isTagEnabled=true flags=0x2
03-23 20:27:25.965  3812  7933 I NotificationService: cancelToast pkg=com.skb.btv.bluetooth callback=android.app.ITransientNotification$Stub$Proxy@9972a90
03-23 20:27:25.966  3812  7933 W NotificationService: Toast already cancelled. pkg=com.skb.btv.bluetooth callback=android.app.ITransientNotification$Stub$Proxy@9972a90
03-23 20:27:25.987  3542  6236 I [Gralloc]: ddebug, pair (share_fd=67, user_hnd=4, ion_client=26)
03-23 20:27:25.988  7455  8294 I [Gralloc]: ddebug, pair (share_fd=57, user_hnd=1, ion_client=60)
03-23 20:27:25.991  3542  6236 I [Gralloc]: ddebug, pair (share_fd=85, user_hnd=5, ion_client=26)
03-23 20:27:25.993  3542  6236 I [Gralloc]: ddebug, pair (share_fd=66, user_hnd=9, ion_client=26)
03-23 20:27:26.032  3812  4787 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ TRACK_DEFAULT id=18, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10050] ], android.os.BinderProxy@95e729a)
03-23 20:27:26.032  3812  6108 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=25, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10050] ], android.os.BinderProxy@13de7cb)
03-23 20:27:26.032  3812  4436 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=18, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10050] ] (release request)
03-23 20:27:26.032  3812  7933 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ TRACK_DEFAULT id=24, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10050] ], android.os.BinderProxy@5fdbba8)
03-23 20:27:26.033  3812  4436 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=24, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10050] ] (release request)
03-23 20:27:26.037  3461  3461 I Zygote  : Process 7075 exited due to signal 9 (Killed)
03-23 20:27:26.042  3812  3863 I libprocessgroup: Successfully killed process cgroup uid 10050 pid 7075 in 88ms
03-23 20:27:26.043  3482  3616 I [Gralloc]: ddebug, pair (share_fd=44, user_hnd=1, ion_client=31)
03-23 20:27:26.663  3522  3522 D isqmsAgent: [isqmsAgent 0893 03/23 20:27:26:663][3522] CISQMSSchedule::SCHETYPE_CYCLE event_id=H01
03-23 20:27:26.892  3812  3812 W WindowManager: removeWindowToken: Attempted to remove non-existing token: android.os.Binder@10956fc
03-23 20:27:27.101  5317  6184 D LogAgentGW: TimerClass: check push agent connection.
03-23 20:27:27.148  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(289)] 11B352D5E98E4182B2A3299F857EFB00 Become root
03-23 20:27:27.969  3812  3860 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
03-23 20:27:27.969  3812  3860 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
03-23 20:27:28.402  5957  7280 V ClientState: MqttWireMessage loop (result is null22.)
03-23 20:27:28.402  5957  7280 V ClientState: MqttWireMessage get2-2
03-23 20:27:28.402  5957  7280 D ClientState: [ClientState] ouboundMiliTime: 301001
03-23 20:27:28.402  5957  7280 D ClientState: [ClientState] inBoundMiliTime: 300998
03-23 20:27:28.402  5957  7280 D ClientState: [ClientState] keepAlive: 300000
03-23 20:27:28.402  5957  7280 D ClientState: [ClientState] checkForActivity pingOutstanding false.
03-23 20:27:28.402  5957  7280 V ClientState: MqttWireMessage get3
03-23 20:27:28.402  5957  7280 V ClientState: CommsSender MqttDeliveryToken flush.
03-23 20:27:28.403  5957  7280 D ClientState: [notifySent] lastOutboundActivity: 1616498848403
03-23 20:27:28.403  5957  7280 V ClientState: CommsSender run.
03-23 20:27:28.403  5957  7280 V ClientState: MqttWireMessage get call.
03-23 20:27:28.403  5957  7280 V ClientState: MqttWireMessage loop (result is null11.)
03-23 20:27:28.403  5957  7280 V ClientState: MqttWireMessage get1
03-23 20:27:28.406  5957  7278 I System.out: MqttPingResp create!!!!
03-23 20:27:28.406  5957  7278 D ClientState: [notifyReceived] lastInboundActivity: 1616498848406
03-23 20:27:28.407  5957  7278 D UPNSCallback: [UPNSCallback] pingResponse!
03-23 20:27:28.626  6913  6956 E chromium: [6913:6956:ERROR:ssl_tcp_socket_connector.cc(292)] SSL Connection timed out: 192.168.201.32:10101
03-23 20:27:28.627  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(261)] Failed to connect to parent
03-23 20:27:29.457  3542  3656 I [Gralloc]: ddebug, free share_fd=66, user_hnd=0x9, ion client=26
03-23 20:27:29.457  3542  3656 I [Gralloc]: ddebug, free share_fd=85, user_hnd=0x5, ion client=26
03-23 20:27:29.460  7455  8294 I [Gralloc]: ddebug, free share_fd=57, user_hnd=0x1, ion client=60
03-23 20:27:29.461  3542  6236 E BufferQueueProducer: [Toast#0] disconnect: not connected (req=1)
03-23 20:27:29.461  7455  8294 W libEGL  : EGLNativeWindowType 0xd6b170a8 disconnect failed
03-23 20:27:29.483  3812  6108 W NotificationService: Toast already killed. pkg=com.skb.btv.bluetooth callback=android.app.ITransientNotification$Stub$Proxy@76d329f
03-23 20:27:29.997  3482  3616 I [Gralloc]: ddebug, free share_fd=44, user_hnd=0x1, ion client=31
03-23 20:27:29.997  3482  3616 W gralloc : Warning shared attribute region mapped at free. Unmapping
03-23 20:27:30.013  3542  3542 I [Gralloc]: ddebug, free share_fd=67, user_hnd=0x4, ion client=26
03-23 20:27:30.335  7640  7640 D MDNSService: MDNSMsgHandler() AM_EVENT_CHECK_NETWORK_CONFIG. isConnected : true
03-23 20:27:30.407  3812  3812 W WindowManager: removeWindowToken: Attempted to remove non-existing token: android.os.Binder@f04dc3d
03-23 20:27:30.663  3522  3522 D isqmsAgent: [isqmsAgent 0894 03/23 20:27:30:663][3522] CISQMSSchedule::SCHETYPE_CYCLE event_id=H01
03-23 20:27:33.598  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 05A58FC1662A0BC09482BAA469222FDF; resolving...

03-23 20:27:34.480  6913  6956 I chromium: [6913:6956:INFO:parent_tracker.cc(186)] Root conflict with 2F6F45CA8DA23741B416C86FFB69BF9E; resolving...

03-23 20:27:34.664  3522  3522 D isqmsAgent: [isqmsAgent 0895 03/23 20:27:34:663][3522] CISQMSSchedule::SCHETYPE_CYCLE event_id=H01



03-23 20:27:35.335  7640  7640 D MDNSService: MDNSMsgHandler() AM_EVENT_CHECK_NETWORK_CONFIG. isConnected : true


^C
130|BFX-AT100:/ #
BRM_BA01_connection_fail.log (51,964 bytes)   

(SW) Kerwin Chen

2021-03-24 08:44

developer   ~0006494

Hi Yk Jung,

The previous reply is for issue 3 "Log where STB does not attempt to connect BLE to RCU during RCU Re-Pairing" .
RCU vendor said only STB rebooting will recover so we have to check it first.
As description above, RCU vendor should not do repairing in "Remote & Accessories" of TVSetting.

Per Mr. Yoon said in wechat, we already know there are code 33/code11 during RCU repairing.
It is an existing issue and discussed in https://mantis.cnsbg.foxconn.com/vaas/view.php?id=773.
I've seen your log, there is code 11 error.
But I think it will be success if you do RCU repairing again without rebooting STB.
This is different from RCU vendor's result.

(ALTech) Younkwang Jung

2021-03-24 13:12

developer   ~0006497

Last edited: 2021-03-24 16:52

View 2 revisions

Hi Kerwin Chen

I couldn't check the morning properly because of the meeting or other issues.
anyway I didn't seem to understand well, so I tested it again.
and I didn't enter "Remote & Accessories" of TVSetting.

* logcat_test_1.log
1) BA02 pairing OK when press "*+#" at BA02 RCU
2) BA01 pairing Fail when press "*+#" at BA01 RCU
3) BA01 pairing OK when press "*+#" at BA01 RCU
4) BA02 pairing OK when press "*+#" at BA02 RCU
5) BA01 pairing Fail when press "*+#" at BA01 RCU
6) BA01 pairing Fail when press "*+#" at BA01 RCU
7) BA01 pairing Fail when press "*+#" at BA01 RCU
8) BA01 pairing Fail when press "*+#" at BA01 RCU

* logcat_test_2.log
STB rebooting ( power )
BA01 pairing OK when press "*+#" at BA01 RCU

so please check the log and explain about this.

Thank you
YK.Jung

logcat_test1.log (10,751,215 bytes)
logcat_test2.log (4,434,079 bytes)

(ALTech) SY Yoon

2021-03-24 17:12

developer   ~0006499

Hi Mr. Kerwin Chen,

I attached log below status.
1. Pair RCU to STB.
2. remove pairing information in Google setting.
3. Try to repair same RCU to STB.
4. It fail to repair, but we can find RCU from the Mobile phone

Could you check why this issue happen ?
RCU version is v1.8 BA01.

We know the issue "directed advertising" from RCU.
In this case, Mobile phone and STB cannot find RCU to pair.
But current case is that Mobile phone can find RCU.

Best regards,
SuhYoung YOON

(ALTech) SY Yoon

2021-03-24 17:15

developer   ~0006500

Hi Mr. Kerwin Chen,

I missed log. So I upload here.
Please check it.

BR
SYOON
RCU_Pairing_Issue_0324.zip (2,578,974 bytes)

(ALTech) Younkwang Jung

2021-03-24 17:40

developer   ~0006501

Hi Kerwin

I attached log file ( btsnoop / logcat )

my test step is below :
1) BA02 pairing OK when press "*+#" at BA02 RCU
2) BA01 pairing OK when press "*+#" at BA01 RCU
3) BA02 pairing OK when press "*+#" at BA02 RCU
4) BA01 pairing Fail when press "*+#" at BA01 RCU
5) BA01 pairing Fail when press "*+#" at BA01 RCU
6) BA01 pairing OK when press "*+#" at BA01 RCU
7) BA02 pairing OK when press "*+#" at BA02 RCU
8) BA01 pairing Fail when press "*+#" at BA01 RCU

so please check the log and explain about this.

Thanks
btsnoop_hci.log (502,864 bytes)
logcat.zip (949,126 bytes)

(ALTech) Younkwang Jung

2021-03-25 17:28

developer   ~0006509

Hi Kerwin

Attach log file and btsnoop file.

There have been about 20 errors.
This is the log I received from QA team.

Please check it
Thank you.
logcat.log (20,758,615 bytes)
btsnoop_hci_0325.log (380,651 bytes)

(SW) Kerwin Chen

2021-03-26 08:44

developer   ~0006511

Hi Mr. YK Jung,

Currently, we can reproduce this issue and still look for solution.
It looks like a status sync problem in Android's Bluetooth service.

In the beginning, we guess problem may be in BT stack so we increase debug level in BT stack.
But it becomes difficult to reproduce.
After checking your log and snoop file, we think problem is not in BT stack.
When issue happens, there is no "create connection" sent from STB after "createBond()" is called.
Now we are checking state machine in Bluetooth service and hope we can solve it soon.

Thanks !

(ALTech) Younkwang Jung

2021-03-26 09:36

developer   ~0006512

Hi Kerwin

Thank you. I will update the progress with SKB manager
and I will check logs again after meeting.

Please let me know if there is any update.

Thanks!

(ALTech) Younkwang Jung

2021-03-26 14:43

developer   ~0006513

Last edited: 2021-03-26 14:46

View 3 revisions

Hi Kerwin

I don't think there's an issue in the STB of INTEK.
I attached the INTEK's log here.
When I trying to pair with BA01, there were 2 times errors, but the pairing was OK on the next attempt.
If you compare our log with INTEC, there will be a clue.

In addition, INNOPIA has the same issue as us.

Thanks!!

btsnoop_hci-2.log (1,679,497 bytes)

(SW) Kerwin Chen

2021-03-30 08:54

developer   ~0006517

Hi Mr. YK Jung,

The fix is committed to BitBucket and will be included in next release.
Thank for your help.

kerwin.chen@fii-foxconn.com | 826e2b4 | [BTVQ-20031] Fix RCU pairing keep failed issue

(ALTech) Younkwang Jung

2021-03-30 09:21

developer   ~0006520

HI Kerwin

Thanks
I'm going to request a test FW this afternoon. our QA team will check it again
and let you know the result.

Thank you for your support
YK.Jung

(ALTech) Younkwang Jung

2021-03-30 09:41

developer   ~0006521

Hi Kerwin

Could you explain the fixed part? ( what is the cause and how you fixed it. )
I have to explain this to SKB.

Thanks
YK.Jung

(SW) Kerwin Chen

2021-03-30 10:01

developer   ~0006522

Hi Mr. YK Jung,

There are lists to store status updates of BT device in BT service.
For BA01 RCU, both BLE and A2DP will communicate with STB.
If the order of BT events are arrived in wrong sequence, BT service will not handle these events well.
And then put that BT device into 'pending' state.
Therefore, 'createBond' won't do connection creation for that device.
Pairing will be failed.

We fix the logic to handle BT events so that no device will be put into 'pending' state no matter which event comes first.

(ALTech) Younkwang Jung

2021-03-30 16:12

developer   ~0006528

Last edited: 2021-03-30 16:17

View 3 revisions

Hi Kerwin

QA team tested it with the FW that you modified. ( FW : v15.523.6c )
but the pairing issue continues to occur. (The same issue is occurring as before)
Please check it again.

Thanks
YK.Jung

btsnoop_hci_0330.log (465,489 bytes)
logcat-2.zip (2,430,843 bytes)

(SW) Kerwin Chen

2021-03-30 17:21

developer   ~0006529

Hi Mr. YK Jung,

Per explained in previous post, the fix is to solve no "create connection" after createBond is called.
From your log, it doesn't happen.
Please try more times, thanks!


03-30 16:53:38.420 7492 7492 I BluetoothDevice: createBond() for device 00:13:7B:76:DD:2E called by pid: 7492 tid: 7492
....
03-30 16:53:38.428 4184 4547 I BluetoothBondStateMachine: Bond address is:00:13:7B:76:DD:2E
....

(ALTech) Younkwang Jung

2021-03-30 18:06

developer   ~0006531

Hi Kerwin

QA team ended early today. the log will be delivered tomorrow.

I'll just ask you one more question.
Didn't you have this issue when you tested it?
Is this issue not reproduced in FXN but only here?

thanks

(SW) Kerwin Chen

2021-03-30 19:07

developer   ~0006532

Hi Mr. YK Jung,

I share our test results here.
Please check it.

https://docs.google.com/spreadsheets/d/1QeCXaUXrFuhqBSivfEp4abLMnBL7ndP4jjNPNOGlUz4/edit#gid=0

(ALTech) Younkwang Jung

2021-03-31 09:21

developer   ~0006534

Hi Kerwin

QA Team tried about 50 times RCU cross-pairs test.
Attach the logs.

When checking the test results,
1) attempts to pair to BA01 after the BA02 pairing always result in a failure.
2) Code11/33 error occurs when pairing fails, but sometimes pairing fails without any error popup.

Please check this log.
Thank you.
YK.Jung
btsnoop_hci_0331.log (3,283,870 bytes)

(ALTech) Younkwang Jung

2021-04-01 10:02

developer   ~0006546

Reminder sent to: (SW) Kerwin Chen

(ALTech) Younkwang Jung

2021-04-01 13:21

developer   ~0006551

Hi Kerwin

I checked again with Google the results you tested before.
If pairing is ok at BA01, you have to pair with BA02.
However, you kept testing with BA01 when BA01 was OK. ( so, there are a lot of pass in the test result. )

If you try to pair with BA01 after BA02 pairing, you will also get a lot of failures.

Thanks

(SW) Kerwin Chen

2021-04-01 13:36

developer   ~0006552

Hi Mr. YK Jung,

We know the issue and still debugging on it.
In other words, there are 2 issues:
1. BA01 keep failed to pair (more than 5 times) after BA02 pairing ==> solved already
2. BA01 pair failed (1 time) after BA02 pairing ==> still under debugging

Thanks !

(ALTech) Younkwang Jung

2021-04-07 08:29

developer   ~0006592

Reminder sent to: (SW) Kerwin Chen

(ALTech) Younkwang Jung

2021-04-08 15:07

developer   ~0006634

Hi Kerwin

Please update the progress on this issue.
and until when can this issue be solved?

Thanks!

(ALTech) Younkwang Jung

2021-04-09 07:54

developer   ~0006644

Reminder sent to: (SW) Kerwin Chen

(SW) Kerwin Chen

2021-04-09 10:30

developer   ~0006646

Hi Mr. YK Jung,

Could you identify the priority of this issue (2)?
For end users, I think they won't have such issue because users have only 1 RCU.
This is why we solve issue (1) first.

As you know, we have many VoC issues on current software release.
Now we are trying to reproduce 1/4 screen issue with different TV models.
I think we will check issue(2) after VoC rate decreases.
Thanks !

(ALTech) Younkwang Jung

2021-04-09 12:03

developer   ~0006648

Hi Kerwin

This issue is also important because it is registered as a BMT issue.
SKB manager is continuing to check this issue.
Please check this issue as well.

And if you can't do it right now, can you solve it by next Wednesday?

Thanks!
YK.Jung

(ALTech) Younkwang Jung

2021-04-13 16:54

developer   ~0006692

Hi Kerwin

If you can't fix this issue right now,
Please let me know the schedule until when it can be solved.
I am going to discuss the schedule with the skb manager.

Thanks!
YK.Jung

(SW) Kerwin Chen

2021-04-13 20:14

developer   ~0006696

Hi Mr. YK Jung,

I did some tests on issue 1).
It looks that it is related to RCU firmware. (I am using BRM RCUs)
For v1.8 firmware, STB usually takes long time at querying GATT services. (more than 10 seconds)
After BLE pairing is done, STB doesn't have enough time to pair with BRM_Audio_BA01(A2DP).
So the result will be failed.

For v1.4 RCU firmware, there is no such issue as described above.
Please help to check with RCU vendor about changes logs from v1.4 to v1.8
Thanks !

(SW) Jacky Chiang

2021-04-14 09:46

manager   ~0006701

Hi Mr. Jung,

     Could you kindly help to forward our suspect in RCU F/W v1.8 to RCU vendor ?

(ALTech) SY Yoon

2021-04-14 10:22

developer   ~0006704

Hi Mr. Kerwin Chen and Mr. Jacky Chiang,

Do you have any log or air log about it ?
If you provide it, then we can forward and explain to RCU Vendors.

(ALTech) Younkwang Jung

2021-04-14 10:28

developer   ~0006705

Hi Jacky , Kerwin

I have forwarded this information to SKB manager and will let you know if there is any update.

Thanks
YK.Jung

(ALTech) Younkwang Jung

2021-06-23 14:25

developer   ~0007537

Hi Jacky , Kerwin

I think this issue has been resolved
I will reopen it if the same issue occurs later.

Thank you for your help
YK.Jung

Issue History

Date Modified Username Field Change
2021-03-18 13:06 (ALTech) Younkwang Jung New Issue
2021-03-18 13:06 (ALTech) Younkwang Jung Status new => assigned
2021-03-18 13:06 (ALTech) Younkwang Jung Assigned To => (SW) Kerwin Chen
2021-03-18 13:06 (ALTech) Younkwang Jung Issue Monitored: (ALTech) SY Yoon
2021-03-18 13:07 (ALTech) Younkwang Jung Issue Monitored: (SW) River Wong
2021-03-19 10:37 (ALTech) Younkwang Jung File Added: 210318_BMM_BA02_STB_Not_Try_to_BLE_Connection.zip
2021-03-19 10:37 (ALTech) Younkwang Jung File Added: BFX-AT100_20210318-205738.zip
2021-03-19 10:37 (ALTech) Younkwang Jung File Added: 210318_BMM_BA01_Repairing_On_DirectAdvertising[STB_Bonded_Info_Erased].zip
2021-03-19 10:37 (ALTech) Younkwang Jung File Added: BFX-AT100_20210318-205306.zip
2021-03-19 10:37 (ALTech) Younkwang Jung File Added: 210318_BMM_BA01_First_Pairing_BLE.zip
2021-03-19 10:37 (ALTech) Younkwang Jung File Added: BFX-AT100_20210318-211203.zip
2021-03-19 10:37 (ALTech) Younkwang Jung Note Added: 0006450
2021-03-22 10:15 (ALTech) Younkwang Jung Note Added: 0006472
2021-03-23 08:01 (ALTech) Younkwang Jung Note Added: 0006481
2021-03-23 14:07 (SW) Kerwin Chen Note Added: 0006485
2021-03-23 16:34 (SW) Jacky Chiang Issue Monitored: (SW) Jim Chen
2021-03-23 20:11 (SW) Kerwin Chen Note Added: 0006490
2021-03-23 20:53 (ALTech) Younkwang Jung File Added: BRM_BA01_connection_fail.log
2021-03-23 20:53 (ALTech) Younkwang Jung File Added: BRM_BA01_connection_ok.log
2021-03-23 20:53 (ALTech) Younkwang Jung Note Added: 0006492
2021-03-24 08:44 (SW) Kerwin Chen Note Added: 0006494
2021-03-24 13:12 (ALTech) Younkwang Jung File Added: logcat_test1.log
2021-03-24 13:12 (ALTech) Younkwang Jung File Added: logcat_test2.log
2021-03-24 13:12 (ALTech) Younkwang Jung Note Added: 0006497
2021-03-24 16:52 (ALTech) Younkwang Jung Note Edited: 0006497 View Revisions
2021-03-24 17:12 (ALTech) SY Yoon Note Added: 0006499
2021-03-24 17:15 (ALTech) SY Yoon File Added: RCU_Pairing_Issue_0324.zip
2021-03-24 17:15 (ALTech) SY Yoon Note Added: 0006500
2021-03-24 17:40 (ALTech) Younkwang Jung File Added: btsnoop_hci.log
2021-03-24 17:40 (ALTech) Younkwang Jung File Added: logcat.zip
2021-03-24 17:40 (ALTech) Younkwang Jung Note Added: 0006501
2021-03-25 17:28 (ALTech) Younkwang Jung File Added: logcat.log
2021-03-25 17:28 (ALTech) Younkwang Jung File Added: btsnoop_hci_0325.log
2021-03-25 17:28 (ALTech) Younkwang Jung Note Added: 0006509
2021-03-26 08:44 (SW) Kerwin Chen Note Added: 0006511
2021-03-26 09:36 (ALTech) Younkwang Jung Note Added: 0006512
2021-03-26 14:43 (ALTech) Younkwang Jung File Added: BID-AT200_20210326-152353.zip
2021-03-26 14:43 (ALTech) Younkwang Jung File Added: btsnoop_hci-2.log
2021-03-26 14:43 (ALTech) Younkwang Jung Note Added: 0006513
2021-03-26 14:43 (ALTech) Younkwang Jung Note Edited: 0006513 View Revisions
2021-03-26 14:46 (ALTech) Younkwang Jung Note Edited: 0006513 View Revisions
2021-03-30 08:54 (SW) Kerwin Chen Note Added: 0006517
2021-03-30 08:55 (SW) Kerwin Chen Assigned To (SW) Kerwin Chen => (ALTech) Younkwang Jung
2021-03-30 08:55 (SW) Kerwin Chen Status assigned => resolved
2021-03-30 08:55 (SW) Kerwin Chen Resolution open => fixed
2021-03-30 09:21 (ALTech) Younkwang Jung Note Added: 0006520
2021-03-30 09:41 (ALTech) Younkwang Jung Note Added: 0006521
2021-03-30 10:01 (SW) Kerwin Chen Note Added: 0006522
2021-03-30 16:12 (ALTech) Younkwang Jung File Added: btsnoop_hci_0330.log
2021-03-30 16:12 (ALTech) Younkwang Jung File Added: logcat-2.zip
2021-03-30 16:12 (ALTech) Younkwang Jung Note Added: 0006528
2021-03-30 16:14 (ALTech) Younkwang Jung Note Edited: 0006528 View Revisions
2021-03-30 16:17 (ALTech) Younkwang Jung Note Edited: 0006528 View Revisions
2021-03-30 17:21 (SW) Kerwin Chen Note Added: 0006529
2021-03-30 18:06 (ALTech) Younkwang Jung Note Added: 0006531
2021-03-30 19:07 (SW) Kerwin Chen Note Added: 0006532
2021-03-31 09:21 (ALTech) Younkwang Jung File Added: BFX-AT100_20210331-084842.zip
2021-03-31 09:21 (ALTech) Younkwang Jung File Added: btsnoop_hci_0331.log
2021-03-31 09:21 (ALTech) Younkwang Jung Note Added: 0006534
2021-04-01 10:02 (ALTech) Younkwang Jung Status resolved => feedback
2021-04-01 10:02 (ALTech) Younkwang Jung Resolution fixed => reopened
2021-04-01 10:02 (ALTech) Younkwang Jung Issue Monitored: (SW) Kerwin Chen
2021-04-01 10:02 (ALTech) Younkwang Jung Note Added: 0006546
2021-04-01 13:09 (ALTech) SY Yoon Assigned To (ALTech) Younkwang Jung => (SW) Kerwin Chen
2021-04-01 13:21 (ALTech) Younkwang Jung Note Added: 0006551
2021-04-01 13:21 (ALTech) Younkwang Jung Status feedback => assigned
2021-04-01 13:36 (SW) Kerwin Chen Note Added: 0006552
2021-04-07 08:29 (ALTech) Younkwang Jung Note Added: 0006592
2021-04-08 15:07 (ALTech) Younkwang Jung Note Added: 0006634
2021-04-09 07:54 (ALTech) Younkwang Jung Note Added: 0006644
2021-04-09 10:30 (SW) Kerwin Chen Note Added: 0006646
2021-04-09 12:03 (ALTech) Younkwang Jung Note Added: 0006648
2021-04-13 16:54 (ALTech) Younkwang Jung Note Added: 0006692
2021-04-13 20:14 (SW) Kerwin Chen Note Added: 0006696
2021-04-14 09:46 (SW) Jacky Chiang Note Added: 0006701
2021-04-14 10:22 (ALTech) SY Yoon Note Added: 0006704
2021-04-14 10:28 (ALTech) Younkwang Jung Note Added: 0006705
2021-06-23 14:25 (ALTech) Younkwang Jung Status assigned => closed
2021-06-23 14:25 (ALTech) Younkwang Jung Note Added: 0007537